Perform single copy + pointer select instead of double write for small types #29
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…l types A previous optimization is no longer deemed worth it, new test results and understanding suggest that a single call to ptr::copy_nonoverlapping per element is more efficient for large input that don't fit into the last level cache. As well as for types like f128.
orlp
approved these changes
Dec 11, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A previous optimization is no longer deemed worth it, new test results and understanding suggest that a single call to ptr::copy_nonoverlapping per element is more efficient for large input that don't fit into the last level cache. As well as for types like f128.
Zen 3 results
Firestorm results:
Icestorm results, honestly those look quite wonky, not sure if they should be trusted